Skip to content

TUI and REST metrics improvements#23328

Closed
davsclaus wants to merge 3 commits into
apache:mainfrom
davsclaus:worktree-more-tui
Closed

TUI and REST metrics improvements#23328
davsclaus wants to merge 3 commits into
apache:mainfrom
davsclaus:worktree-more-tui

Conversation

@davsclaus
Copy link
Copy Markdown
Contributor

Summary

  • Fix tab badge counters mapped to wrong tab indices in TUI (HTTP tab was at index 8 instead of 5)
  • CAMEL-23554: Track InOut consumer replies as "out" hits in DefaultRuntimeEndpointRegistry so endpoints like platform-http show both in and out counters
  • CAMEL-23555: Add per-operation HTTP metrics for REST services in RestRegistry (both code-first and contract-first), exposed via RestDevConsole and displayed in TUI HTTP tab TOTAL column

Test plan

  • Verify TUI badge counters show correct counts for each tab
  • Verify InOut consumers (platform-http) show "out" hits in endpoint tab after processing requests
  • Verify contract-first REST services show per-operation TOTAL counts in HTTP tab
  • Verify code-first REST services show per-operation TOTAL counts via ExchangeCreatedEvent
  • Build all affected modules: camel-api, camel-rest, camel-rest-openapi, camel-console, camel-base-engine, camel-jbang-plugin-tui
  • Run integration tests for camel-rest and camel-rest-openapi

🤖 Generated with Claude Code on behalf of Claus Ibsen

davsclaus and others added 3 commits May 19, 2026 12:36
Badge counters for HTTP, Health, Inspect, and Circuit Breaker tabs were
off-by-one because HTTP was placed last instead of at its correct position.
Use TAB_* constants instead of raw integers to prevent future mismatches.

Co-Authored-By: Claude <noreply@anthropic.com>
…in endpoint statistics

InOut consumers like platform-http send a response back to the client,
but only the inbound request was tracked. Now when an InOut exchange
completes (or fails), an "out" hit is recorded on the consumer's
fromEndpoint so the endpoint tab and flow diagram show both directions.

Co-Authored-By: Claude <noreply@anthropic.com>
…stry

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@davsclaus
Copy link
Copy Markdown
Contributor Author

Recreating PR from apache/camel branch directly.

@github-actions
Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@github-actions
Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • components/camel-rest-openapi
  • components/camel-rest
  • core/camel-api
  • core/camel-base-engine
  • core/camel-console
  • dsl/camel-jbang/camel-jbang-plugin-tui

ℹ️ Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the test-dependents label to force testing all dependents.

Build reactor — dependencies compiled but only changed modules were tested (6 modules)
  • Camel :: API
  • Camel :: Base Engine
  • Camel :: Console
  • Camel :: JBang :: Plugin :: TUI
  • Camel :: REST
  • Camel :: REST OpenApi

⚙️ View full build and test results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant